Skip to main content
This forum is closed to new posts and responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Previous Next
Subject: Directory Assistance, LDAP and multiple NICs
Feedback Type: Question
Product Area: Domino Server
Technical Area: Administration
Platform: Windows
Release: 8.5.3
Reproducible: Unknown

Hi, I wonder if anyone could shed some light on this for me? I'm running a Domino 8.5.3 server and I'm attempting to use Directory Assistance via LDAP to an Active Directory Domain Controller with the following config and issues:

a) The Domino server is in a cluster and has two NICs, one configured with an IP address of 10.x.x.x (the LAN, also the first bound NIC in the server) and one configured with an IP of 192.168.x.x (the cluster network).

b) The DC that DA is doing the LDAP lookups to is on the same 10.x.x.x subnet as the Domino server.

c) When configuring the DA document I can verify all the LDAP configuration items ok but when trying to use DA to authenticate with debugging switched on I get the following logged:

[121C:011F-1090] 03/26/2012 10:59:58.13 AM DA> DirAssist: Name * matches Rule ///// for Domain=<my AD domain>!
[121C:011F-1090] NAMELookup::<NextNameDatabase> DAResolveDomain found 1 directories: <my AD domain>.
[121C:011F-1090] NAMELookup::<NextNameDatabase> looking for directory <my AD domain> in OPEN_NAME_COLLECTION queue for NRPC Clients.
[121C:011F-1090] NAMELookup::<NextNameDatabase> Could not find directory <my AD domain> in OPEN_NAME_COLLECTION queue!

d) To try and see exactly what was going on I ran Wireshark on the Domino server and the problem seems to be that when I'm running the 'verify' process in the DA document, the Domino server is sucessfully contacting the DC from the 10.x.x.x NIC. However, when DA is actually trying to perform the lookup it seems to be trying to do it on the cluster NIC (192.168.x.x).

My question then is why does the Directory Assistance task attempt to perform LDAP lookups on the wrong NIC and how do I force it to use the correct one?


Feedback number WEBB8SREVA created by ~Martha Zekfoolitings on 03/26/2012

Status: Open
Comments:

Directory Assistance, LDAP and mult... (~Martha Zekfool... 26.Mar.12)
. . LDAPNotesPort (~Naomi Minhipit... 26.Mar.12)




Printer-friendly

Search this forum

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS